Method, system and apparatus of time-division-duplex (TDD) uplink-downlink (UL-DL) configuration management

ABSTRACT

Some demonstrative embodiments include devices, systems and/or methods of Time-Division Duplexing (TDD) Uplink-Downlink (UL-DL) configuration management. For example, a node may communicate a message including a cell identifier identifying a first cell controlled by the node, and a TDD configuration update to update at least one other node, which controls at least one second cell, with a TDD UL-DL configuration allocated by the node for communication within the first cell.

CROSS REFERENCE

This application is a continuation of, claims the benefit of andpriority to U.S. patent application Ser. No. 13/681,508 entitled“METHOD, SYSTEM AND APPARATUS OF TIME-DIVISION-DUPLEX (TDD)UPLINK-DOWNLINK (UL-DL) CONFIGURATION MANAGEMENT” and filed Nov. 20,2012, which claims the benefit of and priority to U.S. ProvisionalPatent Application No. 61/646,223 entitled “Advanced WirelessCommunication Systems and Techniques”, filed May 11, 2012, both of whichare incorporated herein by reference in their entirety.

BACKGROUND

Traffic communicated in a communication network, e.g., a cellularnetwork, may often be asymmetrical in time or cell domains. Forinstance, the amount of Downlink (DL) and Uplink (UL) traffic may besignificantly different and may vary in time and/or across differentcells. Such traffic variation may be handled effectively, for example,by adapting the amount of time resources assigned to the DL and the UL,e.g. using different Time Division Duplexing (TDD) frame configurations.

TDD offers flexible deployments without requiring a pair of spectrumresources. For TDD deployments in general, interference between UL andDL including both Base Station (BS) to BS and User Equipment (UE) to UEinterference needs to be considered. One example includes layeredheterogeneous network deployments, where it may be of interest toconsider different uplink-downlink configurations in different cells.Also of interest are deployments involving different carriers deployedby different operators in the same band and employing either the same ordifferent uplink-downlink configurations, where possible interferencemay include adjacent channel interference as well as co-channelinterference such as remote BS-to-BS interference.

Currently, Long-Term-Evolution (LTE) TDD allows for asymmetric UL-DLallocations by providing a semi-static allocation utilizing sevendifferent semi-statically configured uplink-downlink configurations. Thesemi-static allocation may or may not match the actual instantaneoustraffic situation.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a cellular system,in accordance with some demonstrative embodiments.

FIG. 2 is a schematic block diagram illustration of a cellular node, inaccordance with some demonstrative embodiments.

FIG. 3 is a schematic flow-chart illustration of a method ofTime-Division-Duplex (TDD) Uplink-Downlink (UL-DL) configurationmanagement, in accordance with some demonstrative embodiments.

FIG. 4 is a schematic illustration of a product, in accordance with somedemonstrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality”, as used herein, include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

References to “one embodiment,” “an embodiment,” “demonstrativeembodiment,” “various embodiments,” etc., indicate that theembodiment(s) so described may include a particular feature, structure,or characteristic, but not every embodiment necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one embodiment” does not necessarily refer to the sameembodiment, although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first,” “second,” “third,” etc., to describe a commonobject, merely indicate that different instances of like objects arebeing referred to, and are not intended to imply that the objects sodescribed must be in a given sequence, either temporally, spatially, inranking, or in any other manner.

Some embodiments may be used in conjunction with various devices andsystems, for example, a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, a Smartphone device, a server computer, a handheld computer, ahandheld device, a Personal Digital Assistant (PDA) device, a handheldPDA device, an on-board device, an off-board device, a hybrid device, avehicular device, a non-vehicular device, a mobile or portable device, aconsumer device, a non-mobile or non-portable device, a wirelesscommunication station, a wireless communication device, a wirelessAccess Point (AP), a wired or wireless router, a wired or wirelessmodem, a video device, an audio device, an audio-video (A/V) device, awired or wireless network, cellular network, a cellular node, a MultipleInput Multiple Output (MIMO) transceiver or device, a Single InputMultiple Output (SIMO) transceiver or device, a Multiple Input SingleOutput (MISO) transceiver or device, a device having one or moreinternal antennas and/or external antennas, Digital Video Broadcast(DVB) devices or systems, multi-standard radio devices or systems, awired or wireless handheld device, e.g., a Smartphone, a WirelessApplication Protocol (WAP) device, vending machines, sell terminals, andthe like.

Some embodiments may be used in conjunction with devices and/or networksoperating in accordance with existing Long Term Evolution (LTE)specifications, e.g., 3GPP TS 36.423: Evolved Universal TerrestrialRadio Access Network (E-UTRAN); X2 Application Protocol (X2AP) (“RAN3”), 3GPP TS 36.201: “Evolved Universal Terrestrial Radio Access(E-UTRA); Physical Layer—General Description” (“RAN 1”), and/or futureversions and/or derivatives thereof, units and/or devices which are partof the above networks, and the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Frequency-Division Multiplexing (FDM), Orthogonal FDM(OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA),Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA),Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extendedGPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation(MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System(GPS), Wireless Fidelity (Wi-Fi), Wi-Max, ZigBee™, Ultra-Wideband (UWB),Global System for Mobile communication (GSM), second generation (2G),2.5G, 3G, 3.5G, 4G, Long Term Evolution (LTE) cellular system, LTEadvance cellular system, High-Speed Downlink Packet Access (HSDPA),High-Speed Uplink Packet Access (HSUPA), High-Speed Packet Access(HSPA), HSPA+, Single Carrier Radio Transmission Technology (1XRTT),Evolution-Data Optimized (EV-DO), Enhanced Data rates for GSM Evolution(EDGE), and the like. Other embodiments may be used in various otherdevices, systems and/or networks.

The phrase “wireless device”, as used herein, includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the phrase “wireless device” may optionallyinclude a wireless service.

The term “communicating” as used herein with respect to a wirelesscommunication signal includes transmitting the wireless communicationsignal and/or receiving the wireless communication signal. For example,a wireless communication unit, which is capable of communicating awireless communication signal, may include a wireless transmitter totransmit the wireless communication signal to at least one otherwireless communication unit, and/or a wireless communication receiver toreceive the wireless communication signal from at least one otherwireless communication unit.

Some demonstrative embodiments are described herein with respect to aLTE cellular system. However, other embodiments may be implemented inany other suitable cellular network, e.g., a 3G cellular network, a 4Gcellular network, a WiMax cellular network, and the like.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In someembodiments, the antenna may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, the antenna may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements. The antenna may include, for example, a phased array antenna,a single element antenna, a dipole antenna, a set of switched beamantennas, and/or the like.

The term “cell”, as used herein, may include a combination of networkresources, for example, downlink and optionally uplink resources. Theresources may be controlled and/or allocated, for example, by a cellularnode (“also referred to as a “base station”), or the like. The linkingbetween a carrier frequency of the downlink resources and a carrierfrequency of the uplink resources may be indicated in system informationtransmitted on the downlink resources.

Reference is now made to FIG. 1, which schematically illustrates a blockdiagram of a cellular system 100, in accordance with some demonstrativeembodiments. For example, cellular system 100 may include a 4^(th)generation cellular system such as, for example, a WiMAX cellularsystem, a long term evolution (LTE) or LTE advance cellular system, andthe like.

As shown in FIG. 1, in some demonstrative embodiments, system 100 mayinclude a plurality of cellular nodes, e.g., including cellular nodes106 and 108, capable of communicating content, data, information and/orsignals corresponding to a plurality of cells, e.g., including cells 102and 104. For example, node 106 may communicate with a plurality of UserEquipment (UE) devices 110 within cell 102 and/or node 108 maycommunicate with a plurality of UE devices 112 within cell 104.

In some demonstrative embodiments, nodes 106 and/or 108 may include anEvolved Node B (eNB). For example, nodes 106 and/or 108 may beconfigured to perform radio resource management (RRM), radio bearercontrol, radio admission control (access control), connection mobilitymanagement, resource scheduling between UEs and eNB radios, e.g.,Dynamic allocation of resources to UEs in both uplink and downlink,header compression, link encryption of user data streams, packet routingof user data towards a destination, e.g., another eNB or an EvolvedPacket Core (EPC), scheduling and/or transmitting paging messages, e.g.,incoming calls and/or connection requests, broadcast informationcoordination, measurement reporting, and/or any other operations.

In other embodiments, nodes 106 and/or 108 may include any otherfunctionality and/or may perform the functionality of any other cellularnode, e.g., a Node B (NB).

In some demonstrative embodiments, UEs 110 and/or 112 may include, forexample, a mobile computer, a laptop computer, a notebook computer, atablet computer, a mobile internet device, a handheld computer, ahandheld device, a storage device, a PDA device, a handheld PDA device,an on-board device, an off-board device, a hybrid device (e.g.,combining cellular phone functionalities with PDA devicefunctionalities), a consumer device, a vehicular device, a non-vehiculardevice, a mobile or portable device, a mobile phone, a cellulartelephone, a PCS device, a mobile or portable GPS device, a DVB device,a relatively small computing device, a non-desktop computer, a “CarrySmall Live Large” (CSLL) device, an Ultra Mobile Device (UMD), an UltraMobile PC (UMPC), a Mobile Internet Device (MID), an “Origami” device orcomputing device, a video device, an audio device, an A/V device, agaming device, a media player, a Smartphone, or the like.

Reference is made to FIG. 2, which schematically illustrates a cellularnode 200, in accordance with some demonstrative embodiments. Forexample, cellular node 200 may perform the functionality of node 106(FIG. 1) and/or node 108 (FIG. 1).

In some demonstrative embodiments, cellular node 200 may include one ormore wireless communication units 202 to perform wireless communicationbetween node 200 and one or more other devices, e.g., one or more othercellular nodes, UEs, and the like.

In some demonstrative embodiments, wireless communication unit 202 mayinclude, or may be associated with, one or more antennas. In oneexample, wireless communication unit 202 may be associated with at leasttwo antennas, e.g., antennas 208 and 210.

In some demonstrative embodiments, antennas 208 and/or 210 may includeany type of antennas suitable for transmitting and/or receiving wirelesscommunication signals, blocks, frames, transmission streams, packets,messages and/or data. For example, antennas 208 and/or 210 may includeany suitable configuration, structure and/or arrangement of one or moreantenna elements, components, units, assemblies and/or arrays. Forexample, antennas 208 and/or 210 may include a phased array antenna, adipole antenna, a single element antenna, a set of switched beamantennas, and/or the like.

In some embodiments, antennas 208 and/or 210 may implement transmit andreceive functionalities using separate transmit and receive antennaelements. In some embodiments, antennas 208 and/or 210 may implementtransmit and receive functionalities using common and/or integratedtransmit/receive elements.

In some demonstrative embodiments, wireless communication unit 202 mayinclude, for example, at least one radio 204 and at least one controller206 to control communications performed by radio 204. For example, radio204 may include one or more wireless transmitters, receivers and/ortransceivers able to send and/or receive wireless communication signals,RF signals, frames, blocks, transmission streams, packets, messages,data items, and/or data.

In some demonstrative embodiments, radio 204 may include a multipleinput multiple output (MIMO) transmitters receivers system (not shown),which may be capable of performing antenna beamforming methods, ifdesired.

In some demonstrative embodiments, radio 204 may include a turbo decoderand/or a turbo encoder (not shown) for encoding and/or decoding databits into data symbols, if desired.

In some demonstrative embodiments, radio 204 may include OFDM and/orSC-FDMA modulators and/or demodulators (not shown) configured tocommunicate OFDM signals over downlink (DL) channels, e.g., betweencellular node 200 and a UE, and SC-FDMA signals over uplink (UL)channels, e.g., between the UE and cellular node 200.

In some demonstrative embodiments, node 200 may include aTime-Division-Duplexing (TDD) UL-DL configuration controller 230 tocontrol a TDD UL-DL configuration of time resources allocated for the ULand DL communication within a cell controlled by node 200. For example,node 106 (FIG. 1) may include a TDD UL-DL configuration controller 230to control a TDD UL-DL configuration of time resources allocated for theUL and DL communication within cell 102 (FIG. 1); and/or node 108(FIG. 1) may include a TDD UL-DL configuration controller 230 to controla TDD UL-DL configuration of time resources allocated for the UL and DLcommunication within cell 104 (FIG. 1).

In some demonstrative embodiments, TDD UL-DL configuration controller230 may be implemented as part of wireless communication unit 202. Inother embodiments, TDD UL-DL configuration controller 230 and wirelesscommunication unit 202 may be implemented as separate elements of node200 or as a separate network entity that controls dynamic assignment ofUL-DL configuration for multiple cells.

In some demonstrative embodiments, cellular node 200 may include, forexample, one or more of a processor 220, a memory unit 222, and astorage unit 224. In one example, one or more of processor, 220 memory222 and/or storage 224 may be implemented as one or more elementsseparate from wireless communication unit 202 and/or TDD UL/DLconfiguration controller 230. In another example, one or more ofprocessor, 220 memory 222 and/or storage 224 may be implemented as partof wireless communication unit 202 and/or TDD UL/DL configurationcontroller 230.

Processor 220 includes, for example, a Central Processing Unit (CPU), aDigital Signal Processor (DSP), one or more processor cores, asingle-core processor, a dual-core processor, a multiple-core processor,a microprocessor, a host processor, a controller, a plurality ofprocessors or controllers, a chip, a microchip, one or more circuits,circuitry, a logic unit, an Integrated Circuit (IC), anApplication-Specific IC (ASIC), or any other suitable multi-purpose orspecific processor or controller. Processor 220 executes instructions,for example, of an Operating System (OS) of node 200 and/or of one ormore suitable applications.

Memory unit 222 includes, for example, a Random Access Memory (RAM), aRead Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM(SD-RAM), a flash memory, a volatile memory, a non-volatile memory, acache memory, a buffer, a short term memory unit, a long term memoryunit, or other suitable memory units. Storage unit 224 includes, forexample, a hard disk drive, a floppy disk drive, a Compact Disk (CD)drive, a CD-ROM drive, a DVD drive, or other suitable removable ornon-removable storage units. Memory unit 222 and/or storage unit 224,for example, may store data processed by node 200.

Referring back to FIG. 1, in some demonstrative embodiments nodes 106and 108 may be configured to perform TDD UL-DL configuration management,e.g., as described in detail below.

In some demonstrative embodiments, nodes 106 and 108 may communicate TDDUL-DL configuration information. For example, node 106 may transmit tonode 108 TDD UL-DL configuration information relating to a TDD UL-DLconfiguration of cell 102; and/or node 108 may transmit to node 106 TDDUL-DL configuration information relating to a TDD UL-DL configuration ofcell 104, e.g., as described below. In other embodiments the TDD UL-DLconfiguration information may be shared with another network entity,which may define a TDD UL-DL configuration to be used at nodes 106 and108.

Some demonstrative embodiments are described herein with reference to aneNB-to-eNB interface for communicating TDD UL-DL configurationinformation between two eNBs. However, other embodiments may beimplemented with respect to any other interface, e.g., an eNB-to-OAMinterface for communicating the TDD UL-DL configuration informationbetween an eNB and a Operations and Management (OAM) interface betweenthe eNB and an Element Management System (EMS), e.g., a MobilityManagement Entity (MME), and the like.

In some demonstrative embodiments, nodes 106 and 108 may utilize the TDDUL-DL configuration information, for example, for enhanced InterferenceManagement and Traffic Adaptation (eIMTA), and/or for any other purpose.

In some demonstrative embodiments, nodes 106 and 108 may utilize the TDDUL-DL configuration information, for example, for dynamic TDD UL-DLconfiguration. For example, a first node, e.g., node 106, maycommunicate to a second node, e.g., node 108, TDD UL-DL configurationinformation relating to the TDD UL-DL configuration of a cell controlledby the first node, e.g., cell 102. The second node, e.g., node 108, mayadapt, e.g., dynamically adapt, a TDD UL-DL configuration of a cellcontrolled by the second node, e.g., cell 104, based at least on the TDDUL-DL of the first cell. For example, node 108 may dynamically adapt aTDD UL-DL configuration of cell 104 by dynamically taking into accountuplink and downlink traffic and other conditions of cell 102.

In some demonstrative embodiments, node 106 may transmit a messageincluding a TDD UL-DL configuration update to update at least one othernode, e.g., node 108, with a TDD UL-DL configuration allocated by node106, e.g., by the TDD UL-DL configuration controller 230 (FIG. 1) ofnode 106, for communication within cell 102, e.g., as described indetail below.

In some demonstrative embodiments, node 108 may receive the message fromnode 106 and may allocate a TDD UL-DL configuration for communicationwithin cell 104 based on the TDD UL-DL configuration update receivedfrom node 106. For example, the TDD UL-DL configuration controller 230(FIG. 1) of node 108 may allocate the TDD UL-DL configuration forcommunication within cell 104 based on the TDD UL-DL configurationupdate received from node 106.

In some demonstrative embodiments, the message may include an X2Application Protocol (X2AP) message, which may be configured forcommunication between eNBs. In other embodiments, the message mayinclude any other message configured for communication between any othercellular nodes.

In some demonstrative embodiments, the TDD UL-DL configuration updatemay be communicated as part of a dedicated field of X2AP message, e.g.,an existing message type, which may include other fields for otherpredefined purposes.

In some demonstrative embodiments, the TDD UL-DL configuration updatemay be communicated as part of a dedicated X2AP message, e.g., a newmessage type, which may be dedicated for communicating the TDD UL-DLconfiguration update.

In some demonstrative embodiments, communicating the TDD UL-DLconfiguration update as part of an existing message type may bebeneficial, e.g., as having a reduced standardization impact.

In some demonstrative embodiments, communicating the TDD UL-DLconfiguration update as part of a dedicated message may enable providingthe TDD UL-DL configuration update at a timing and/or frequency, whichmay be independent from and/or different from a timing of communicatingthe existing message. For example, communicating the TDD UL-DLconfiguration update as part of a dedicated message may enable providingthe TDD UL-DL update at a frequency, which may higher than a frequencyof a resource status update, e.g., a frequency of less than one second.

In some demonstrative embodiments, the message may also include a cellidentifier identifying the cell corresponding to the TDD UL-DLconfiguration update. For example, node 106 may transmit a messageincluding an identifier of cell 102 and the TDD UL-DL informationcorresponding to cell 102.

In some demonstrative embodiments, the TDD UL-DL configuration updatemay be included as part of a predefined Information Element (IE)(“Dynamic Subframe Assignment IE”).

In some demonstrative embodiments, the TDD UL-DL configuration updatemay be included as part of a message defined for communicating load andinterference coordination information.

For example, the TDD UL-DL configuration update may be included as partof a Load Information X2AP message, which may be communicated from aneNB, e.g., node 106, to one or more neighboring eNBs, e.g., includingeNB 108.

In one example, the Dynamic Subframe Assignment IE may be included aspart of the Load Information X2AP message, e.g., as follows:

TABLE 1 IE type and Semantics Assigned IE/Group Name Presence Rangereference description Criticality Criticality Message Type Mandatory9.2.13 YES ignore (M) Cell Information M YES ignore >Cell InformationItem 1 . . . EACH ignore <maxCellin eNB> >>Cell ID M ECGI Id of the — —9.2.14 source cell >>UL Interference Optional 9.2.17 — — OverloadIndication (O) >>UL High 0 . . . — — Interference <maxCellin InformationeNB> >>>Target Cell ID M ECGI Id of the cell — — 9.2.14 for which theHII is meant >>>UL High M 9.2.18 — — Interference Indication >>RelativeNarrowband O 9.2.19 — — Tx Power (RNTP) >>ABS Information O 9.2.54 YESignore >>Invoke Indication O 9.2.55 YES ignore >>Dynamic Subframe OENUMER- Dynamic — — Assignment ATED(sa0, Uplink- sa1, sa2, sa3, downlinksa4, sa5, subframe sa6, . . . ) configuration information defined inref. TS 36.211 [10] to support adaptive change of UL-DL configurationw/o system information update

The notation ENUMERATED (sa0, sa1, sa2, sa3, sa4, sa5, sa6 . . . ), asused in Table 1, denotes that the Dynamic Subframe Assignment IE mayinclude one of the values denoted “sa”. The values denoted “sa” mayinclude values indicating different TDD UL-DL configurations. Forexample, the values sa0, sa1, sa2, sa3, sa4, sa5, sa6 may indicate sevenrespective predefined TDD UL-DL configurations. In one embodiment, theseven predefined TDD UL-DL configurations may include, for example, TDDUL-DL configurations defined by the LTE Specifications, e.g., as definedby 3GPP TS 36.211 (“Evolved Universal Terrestrial Radio Access (E-UTRA);Physical channels and modulations”). For example, the value sa0 mayrepresent a first predefined allocation of time resources, the value sa1may represent a second predefined allocation of time resources, and soon. In other embodiments, the Dynamic Subframe Assignment IE may includeany other representation of a TDD UL-DL configuration, e.g., selectedfrom any other predefined set of TDD UL-DL configurations and/or definedin any other suitable manner, e.g., with or without referring to one ormore predefined configurations.

Per Table 1, the Load Information X2AP message may include a “Cell ID”IE including a cell identifier identifying the cell to which the DynamicSubframe Assignment IE corresponds, and a target cell identifier,denoted “Target Cell ID”, identifying a cell of a node intended toreceive the Dynamic Subframe Assignment IE.

In some demonstrative embodiments, the TDD UL-DL configuration updatemay be included as part of a message broadcast by an eNB and including aconfiguration update corresponding to the eNB.

For example, the TDD UL-DL configuration update may be included as partof a Configuration Update X2AP message, which may be communicated froman eNB, e.g., node 106, to one or more neighboring eNBs, e.g., includingeNB 108.

In one example, the Dynamic Subframe Assignment IE may be included aspart of a Served Cell Information IE of the Configuration Update X2APmessage, e.g., as follows:

TABLE 2 Pres- IE type and Semantics Assigned IE/Group Name ence Rangereference description Criticality Criticality PCI M INTEGER (0 . . .Physical Cell ID — — 503, . . . ) Cell ID M ECGI — — 9.2.14 TAC M OCTETTracking Area — — STRING(2) Code Broadcast PLMNs 1 . . . Broadcast PLMNs— — <maxnoof BPLMNs> >PLMN Identity M 9.2.4 — — CHOICE EUTRA- M — —Mode-Info >FDD >FDD Info 1 — — >>>UL M EARFCN Corresponds to — — EARFCN9.2.26 N_(UL) in ref. TS 36.104 [16]. >>>DL M EARFCN Corresponds to — —EARFCN 9.2.26 N_(DL) in ref. TS 36.104 [16]. >>>UL M Transmission — —Transmission Bandwidth Bandwidth 9.2 27 >>>DL M Transmission Same as UL— — Transmission Bandwidth Transmission Bandwidth 9.2 27 Bandwidth inthis release. >TDD — — >TDD Info 1 — — >>>EARFCN M 9.2.26 Corresponds to— — N_(DL)/N_(UL) in ref. TS 36.104 [16]. >>>Transmission M Transmission— — Bandwidth Bandwidth 9.2 27 >>>Subframe M ENUMERATED Uplink-downlink— — Assignment (sa0, sa1, sa2, subframe sa3, sa4, sa5, configurationinfor- sa6, . . . ) mation defined in ref. TS 36.211 [10]. >>>Special 1Special subframe — — Subframe Info configuration infor- mation definedin ref. TS 36.211 [10]. >>>>Special M ENUMERATED — — Subframe (ssp0,ssp1, ssp2, Patterns ssp3, ssp4, ssp5, ssp6, ssp7, ssp8, . . .) >>>>Cyclic M ENUMERATED — — Prefix DL (Normal, Extended, . . .) >>>>Cyclic M ENUMERATED — — Prefix UL (Normal, Extended, . . .) >>>Dynamic O ENUMERATED Dynamic Uplink- — — Subframe (sa0, sa1, sa2,downlink subframe Assignment sa3, sa4, sa5, configuration sa6, . . . )information defined in ref. TS 36.211 [10] to support adaptive change ofUL-DL configuration w/o system information update Number of Antenna O9.2.43 YES ignore Ports PRACH O PRACH YES ignore ConfigurationConfiguration 9.2.50 MBSFN Subframe 0 . . . MBSFN subframe GLOBAL ignoreInfo <maxnoofM defined in TS BSFN> 36.331 [9]. >Radioframe M ENUMERATED— — Allocation Period (n1, n2, n4, n8, n16, n32, . . . ) >Radioframe MINTEGER — — Allocation Offset (0 . . . 7, . . . ) >Subframe M 9.2.51 — —Allocation CSG Id O 9.2.53 YES ignore

In some demonstrative embodiments, the TDD UL-DL configuration updatemay be included as part of a dedicated message defined for communicatingthe Dynamic Subframe Assignment IE.

In one example, the Dynamic Subframe Assignment IE may be included aspart of a dedicated TDD configuration update X2AP message, e.g., asfollows:

TABLE 3 Pres- IE type and Semantics Assigned IE/Group Name ence Rangereference description Criticality Criticality Message Type M YES ignoreCell Information M YES ignore >Cell 1 . . . EACH ignore Information<maxCel Item lineNB> >>Cell ID M ECGI Id of the — — 9.2.14 sourcecell >>Subframe O ENUMER- Uplink- — — Assignment ATED(sa0, downlink sa1,sa2, sa3, subframe sa4, sa5, sa6, configuration . . . ) informationdefined in ref. TS 36.211 [10].

In some demonstrative embodiments, nodes 106 and 108 may communicate oneor more additional messages to facilitate dynamic assignment of UL andDL resources and/or to communicate additional information related to theTDD UL-DL configuration utilized by nodes 106 and/or 108 with respect tocells 102 and/or 104, e.g., as described in detail below.

In some demonstrative embodiments, a node, e.g., node 106, may transmitto one or more other nodes, e.g., including node 108, a status reportrelating to UL and/or DL queue states of one or more cells controlled bythe node, e.g., as described below.

In some demonstrative embodiments, the UL-DL queue states may includeone or more parameters characterizing current cell demands for requiredUL and/or DL resources. In one example, the status report may include anestimated number of bits representing an estimated buffer size for ULand/or DL transmission.

In some demonstrative embodiments, nodes 106 and 108 may communicate astatus report of UL-DL queue states corresponding to cells 102 and/or104, e.g., as described below.

In some demonstrative embodiments, a node, e.g., node 106, may receive astatus request message indicating a request from another node (“targetnode”), e.g., node 108, to the node for a status report of UL-DL queuestates corresponding to at least one cell controlled by the node, e.g.,cell 102. The node may transmit a status update message including therequested report, e.g., in response to the status request message.

In some demonstrative embodiments, the status request message and thestatus update message may be communicated as part of an X2AP resourcestatus reporting procedure.

In some demonstrative embodiments, the status request message mayinclude a Resource Status Request message including a ReportCharacteristics IE including a bit, which has a predefined valueindicating the request for the status report, and a ReportingPeriodicity IE defining a requested periodicity, e.g., a minimalperiodicity, at which the node is to transmit the status report to thetarget node.

For example, the Resource Status Request message may include the ReportCharacteristics IE, including a sixth bit to indicate whether the statusreport is requested, and the Reporting Periodicity IE to indicate therequested periodicity, e.g., as follows:

TABLE 4 IE type and Semantics Assigned IE/Group Name Presence Rangereference description Criticality Criticality Message Type M 9.2.13 YESreject eNB1 M INTEGER Allocated by YES reject Measurement ID (1 . . .4095, eNB₁ . . . ) eNB2 C- INTEGER Allocated by YES ignore MeasurementID ifRegistration (1 . . . 4095, eNB₂ RequestStop . . . ) Registration MENUMER- A value set to YES reject Request ATED “stop”, indicates (start,stop, a request to . . . ) stop all cells measurements. Report OBITSTRING Each position in YES reject Characteristics (SIZE(32)) thebitmap indicates measurement object the eNB2 is requested to report.First Bit = PRB Periodic, Second Bit = TNL load Ind Periodic, Third Bit= HW Load Ind Periodic, Fourth Bit = Composite Available CapacityPeriodic, Fifth Bit = ABS Status Periodic. Sixth Bit = UL- DL queuesizes periodic. Other bits shall be ignored by the eNB₂ Cell To Report 1Cell ID list for YES ignore which measurement is needed >Cell To Report1 . . . EACH ignore Item <maxCellin eNB> >>Cell ID M ECGI — — 9.2.14Reporting O ENUMER- YES ignore Periodicity ATED(10 ms, 20 ms, 40 ms, 80ms, 160 ms, 320 ms, 640 ms, 1000 ms, 2000 ms, 5000 ms, 10000 ms, . . . )Partial Success O ENUMER- Included if YES ignore Indicator ATED(partialpartial success success is allowed. allowed, . . . )

For example, the “UL-DL queue sizes periodic” bit may be set to apredefined value, e.g., 1, to indicate that a RESOURCE STATUS UPDATEmessage is to include the UL-DL queue state information, and is to betransmitted from the target node at a periodicity indicated at theReporting Periodicity IE, e.g., as defined below.

In some demonstrative embodiments, the status update message may includea Resource Status Update message including an UL/DL queue state IEincluding an UL queue state and a DL queue state.

For example, the Resource Status Update message may include an UL/DLqueue size IE an UL queue state and a DL queue state, e.g., as follows:

TABLE 5 IE type and Semantics Assigned IE/Group Name Presence Rangereference description Criticality Criticality Message Type M 9.2.13 YESignore eNB1 Measurement ID M INTEGER Allocated by YES reject (1 . . .4095, eNB₁ . . . ) eNB2 Measurement ID M INTEGER Allocated by YES reject(1 . . . 4095, eNB₂ . . . ) >Cell Measurement 1 YES ignore Result >CellMeasurement 1 . . . EACH ignore Result Item <maxCellin eNB> >>Cell ID MECGI 9.2.14 >>Hardware Load O 9.2.34 Indicator >>S1 TNL Load O 9.2.35Indicator >>Radio Resource O 9.2.37 Status >>Composite O 9.2.44 YESignore Available Capacity Group >>ABS Status O 9.2.58 YES ignore >>UL-DLQueue O Sizes

The UL-DL Queue Sizes IE may indicate an estimated buffer size to betransmitted in DL and UL for particular cells of the eNB, whichtransmits the Resource Status Update, e.g., as follows:

TABLE 6 IE/Group IE type and Semantics Name Presence Range referencedescription UL Queue M INTEGER (0 . . . FFS) Size DL Queue M INTEGER (0. . . FFS) Size

In some demonstrative embodiments, the status request message and thestatus update message may be communicated as part of dedicated UL/DLqueue state X2AP messages.

In some demonstrative embodiments, the status request message may betransmitted from a first node to a second node and may include adedicated Buffer Status Request message including a ReportingPeriodicity IE defining a requested periodicity at which the second nodeis to update the first node with the UL-DL queue states. The use of thededicated Buffer Status Request message may enable the first node torequest the second node to report the UL-DL states at a differentfrequency, e.g., a higher frequency, compared, for example, to afrequency at which the second node transmits the Resource Status Updatemessage.

In one example, the Buffer Status Request message may include one ormore identifiers of one or more cells, for which the UL-DL queue statesare requested, and a requested reporting periodicity at which the UL-DLqueue states are to be provided, e.g., as follows:

TABLE 7 Pres- IE type and Semantics Assigned IE/Group Name ence Rangereference description Criticality Criticality Message Type M YES rejectRegistration Request M ENUMERATED A value set to YES reject (start,stop, . . . ) “stop”, indicates a request to stop all cellsmeasurements. Cell To Report 1 Cell ID list for YES ignore whichmeasurement is needed >Cell To Report 1 . . . EACH ignore Item <maxCellineNB> >>Cell ID M ECGI — — 9.2.14 Reporting Periodic- O ENUMERATED YESignore ity (10 ms, 20 ms, 40 ms, 80 ms, 160 ms, 320 ms, 640 ms, 1000 ms,2000 ms,5000 ms, 10000 ms, . . . )

In some demonstrative embodiments, the status update message may betransmitted from the second node to the first node and may include adedicated Buffer Status Update message including the UL-DL queue statesof the cells identified by the status request message. In one example,the dedicated Buffer Status Update message may be transmitted inresponse to the dedicated Buffer Status Request message. In anotherexample, the dedicated Buffer Status Update message may be transmittedin response to the Resource Status Request message described above.

In one example, the dedicated Buffer Status Update message may includethe UL-DL queue states IE, e.g., as follows:

TABLE 8 Pres- IE type and Semantics Assigned IE/Group Name ence Rangereference description Criticality Criticality Message Type M 9.2.13 YESignore Cell Measurement Result 1 YES ignore >Cell Measurement 1 . . .EACH ignore Result Item <maxCellin eNB> >>UL-DL Queue Sizes O

In some demonstrative embodiments, nodes 106 and 108 may communicate atiming message including timing information indicating a timing at whichnode 106 is allowed to update the TDD UL-DL configuration allocated forcell 102 and/or a timing at which node 108 is allowed to update the TDDUL-DL configuration allocated for cell 104. In one example, the timingupdate may be synchronized across multiple cells, if desired.

In some demonstrative embodiments, the timing information may becommunicated as part of an IE, e.g., a Served Cell Information IE,including cell configuration information of one or more cells.

In one example, a first node, e.g., node 106, may transmit, e.g., to asecond node, an eNB Configuration Update message including a Served CellInformation IE, which may include a configuration update Timescale fieldindicating how often the first node is allowed to update the TDD UL-DLconfiguration. For example, the Served Cell Information IE may includethe configuration update Timescale field, e.g., as follows:

TABLE 9 Pres- IE type and Semantics Assigned IE/Group Name ence Rangereference description Criticality Criticality PCI M INTEGER (0 . . .Physical Cell — — 503, . . . ) ID Cell ID M ECGI — — 9.2.14 TAC M OCTETTracking Area — — STRING(2) Code Broadcast PLMNs 1 . . . Broadcast — —<maxnoo PLMNs fBPLMNs> >PLMN Identity M 9.2.4 — — CHOICE EUTRA- M — —Mode-Info >FDD >>FDD Info 1 — — >>>UL M EARFCN Corresponds — — EARFCN9.2.26 to N_(UL) in ref. TS 36.104 [16]. >>>DL M EARFCN Corresponds — —EARFCN 9.2.26 to N_(DL) in ref. TS 36.104 [16]. >>>UL M Transmission — —Transmission Bandwidth Bandwidth 9.2 27 >>>DL M Transmission Same as UL— — Transmission Bandwidth Transmission Bandwidth 9.2 27 Bandwidth inthis release. >TDD — — >>TDD Info 1 — — >>>EARFCN M 9.2.26 Corresponds —— to N_(DL)/N_(UL) in ref. TS 36.104 [16]. >>>Transmission MTransmission — — Bandwidth Bandwidth 9.2 27 >>>Subframe M ENUMERATEDUplink- — — Assignment (sa0, sa1, sa2, sa3, downlink sa4, sa5, sa6, . .. ) subframe configuration information defined in ref. TS 36.211[10]. >>>Special 1 Special — — Subframe Info subframe configurationinformation defined in ref. TS 36.211 [10]. >>>>Special M ENUMERATED — —Subframe (ssp0, ssp1 , ssp2, Patterns ssp3, ssp4, ssp5, ssp6, ssp7,ssp8, . . . ) >>>>Cyclic M ENUMERATED — — Prefix DL (Normal, Extended, .. . ) >>>>Cyclic M ENUMERATED — — Prefix UL (Normal, Extended, . . .) >>>TDD UL- DL Configuration Update Timescale Number of Antenna O9.2.43 YES ignore Ports PRACH O PRACH YES ignore ConfigurationConfiguration 9.2.50 MBSFN Subframe 0 . . . MBSFN GLOBAL ignore Info<maxnoofM subframe BSFN> defined in TS 36.331 [9]. >Radioframe MENUMERATED — — Allocation Period (n1, n2, n4, n8, n16, n32, . . .) >Radioframe M INTEGER (0 . . . — — Allocation Offset 7, . . .) >Subframe M 9.2.51 — — Allocation CSG Id O 9.2.53 YES ignore

The TDD UL-DL Configuration Update Timescale IE may be defined, forexample, as an integer value, for example, within a predefined range,e.g., between 10 milliseconds (ms) and 640 ms; as an enumerated valuefor a limited set of values in the range, e.g., 10 ms, 20 ms, 40 ms, 80ms, 160 ms, 320 ms, and 640 ms, or in any other manner.

In some demonstrative embodiments, the timing information may beconfigured to all eNBs, e.g., to both nodes 106 and 108, for example, byan OAM.

In some demonstrative embodiments, nodes 106 and 108 may communicate anindication of an UL-DL configuration subset selected by node 106 from apredefined set of UL-DL configurations and/or an indication of an UL-DLconfiguration subset selected by node 108 from the predefined set ofUL-DL configurations.

In some demonstrative embodiments, nodes 106 may be configured to selectthe TDD UL-DL configuration from a predefined set of seven TDD UL-DLconfigurations, e.g., as defined by 3GPP TS 36.211.

In some demonstrative embodiments, node 106 may transmit an eNBConfiguration Update message including a Served Cell Information IEincluding a subframe assignment IE indicating one or more allowed UL-DLconfigurations, which is selected by node 106 to be allowed for use byone or more other nodes, e.g., node 108; and/or node 108 may transmit aneNB Configuration Update message including a Served Cell Information IEincluding a subframe assignment IE indicating one or more allowed UL-DLconfigurations, which are selected by node 108 to be allowed for use byone or more other nodes, e.g., node 106. For example, the Served CellInformation IE may include the subframe assignment IE, e.g., as follows:

TABLE 10 Pres- Semantics Assigned IE/Group Name ence Range IE type andreference description Criticality Criticality PCI M INTEGER PhysicalCell ID — — (0 . . . 503, . . . ) Cell ID M ECGI — — 9.2.14 TAC M OCTETSTRING(2) Tracking Area — — Code Broadcast 1 . . . <maxnoof Broadcast —— PLMNs BPLMNs> PLMNs >PLMN Identity M 9.2.4 — — CHOICE EUTRA- M — —Mode-Info >FDD >>FDD Info 1 — — >>>UL M EARFCN Corresponds to — — EARFCN9.2.26 N_(UL) in ref. TS 36.104 [16]. >>>DL M EARFCN Corresponds to — —EARFCN 9.2.26 N_(DL) in ref. TS 36.104 [16]. >>>UL M Transmission — —Transmission Bandwidth Bandwidth 9.2 27 >>>DL M Transmission Same as UL— — Transmission Bandwidth Transmission Bandwidth 9.2 27 Bandwidth inthis release. >TDD — — >>TDD Info 1 — — >>>EARFCN M 9.2.26 Correspondsto — — N_(DL)/N_(UL) in ref. TS 36.104 [16]. >>>Transmission MTransmission — — Bandwidth Bandwidth 9.2 27 >>>Subframe M ENUMERATEDUplink-downlink — — Assignment (sa0, sa1 , sa2, sa3, subframe sa4, sa5,sa6, . . . ) configurationinfor mation defined in ref. TS 36.211[10]. >>>Special 1 Special subframe — — Subframe configurationinfor Infomation defined in ref. TS 36.211 [10]. >>>>Special M ENUMERATED — —Subframe (ssp0, ssp1, ssp2, ssp3, Patterns ssp4, ssp5, ssp6, ssp7, ssp8,. . . ) >>>>Cyclic M ENUMERATED — — Prefix DL (Normal, Extended, . . .) >>>Cyclic M ENUMERATED(No — — Prefix UL rmal, Extended, . . .) >>>Subframe Assignment Subset Number of O 9.2.43 YES ignore AntennaPorts PRACH O PRACH YES ignore Configuration Configuration 9.2.50 MBSFN0 . . . <maxnoo MBSFN GLOBAL ignore Subframe Info fMBSFN> subframedefined in TS 36.331 [9]. >Radioframe M ENUMERATED(n1, n2, — —Allocation Period n4, n8, n16, n32, . . . ) >Radioframe M INTEGER (0..7,. . . ) — — Allocation Offset >Subframe M 9.2.51 — — Allocation CSG Id O9.2.53 YES ignore

In some demonstrative embodiments, the Subframe Assignment Subset IE mayindicate, for example, which one or more subsets out of the seven TDDUL-DL configurations are allowed, by a node transmitting the Served CellInformation IE, to be used by one or more other nodes. In one example,the Subframe Assignment Subset IE may be defined as a bitmap, in which abit is set to a predefined value, e.g., one, to indicate that acorresponding TDD UL-DL configuration is allowed to be used by the oneor more other nodes. For example, a first bit may be set to “1”, whileall other bits are set to zero, to indicate that a first TDD UL-DLconfiguration is to allowed to be used by the one or more other nodes.

In one example, node 106 may transmit the Subframe Assignment Subset IEindicating a plurality of TDD UL-DL configurations, which are allowedfor use. Node 108 may receive the Subframe Assignment Subset IE fromnode 106 and may select a TDD UL-DL configuration from the plurality ofTDD UL-DL configurations indicated as allowed by the Subframe AssignmentSubset IE. Node 108 may transmit a TDD UL-DL configuration update, e.g.,as described above, indicating the TDD UL-DL configuration selected bynode 108.

In some demonstrative embodiments, the TDD UL-DL may be configured to aselected configuration for all eNBs, e.g., both nodes 106 and 108, forexample, by an OAM.

In some demonstrative embodiments, a particular node may communicate toanother node a message including an indication (“spectral efficiencyindication”) of an average UL-DL spectral efficiency for one or morecells controlled by the particular node. For example, nodes 106 and 108may communicate an indication of an average UL-DL spectral efficiencyfor cells 102 and/or 104.

In some demonstrative embodiments, the X2AP resource status reportingprocedure may be utilized to support communication of the spectralefficiency indication, e.g., as described below.

In some demonstrative embodiments, a first node may transmit to a secondnode a request message including a request for the indication of theaverage UL-DL spectral efficiency, and defining a requested periodicityat which the indication of the average UL-DL spectral efficiency is tobe transmitted.

In some demonstrative embodiments, the RESOURCE STATUS REQUEST may betransmitted by the first node to request the second node to communicatethe spectral efficiency indication. For example, an IE of the RESOURCESTATUS REQUEST, e.g., a Report Characteristics IE, may include a bit(“UL-DL spectral efficiency periodic”) to indicate the request for thespectral efficiency indication. In one example, the ReportCharacteristics IE of the RESOURCE STATUS REQUEST of Table 4 may bemodified to include an additional bit, e.g., a seventh bit, to indicatethe request for the spectral efficiency indication. The ReportingPeriodicity IE may also be included, e.g., as described above withreference to Table 4. Alternatively the Buffer Status Request message,as described above with reference to Table 7, may be used.

In some demonstrative embodiments, the second node may transmit aRESOURCE STATUS UPDATE message including average UL and DL spectralefficiency information, e.g., if the “UL-DL spectral efficiencyperiodic” bit is set to a predefined value, e.g., one.

In one example, the RESOURCE STATUS UPDATE message may include an UL-DLSpectral Efficiency IE, e.g., as follows:

TABLE 11 Pres- IE type and Semantics Assigned IE/Group Name ence Rangereference description Criticality Criticality Message Type M 9.2.13 YESignore eNB1 Measurement ID M INTEGER Allocated by YES reject (1 . . .4095, eNB₁ . . . ) eNB2 Measurement ID M INTEGER Allocated by YES reject(1 . . . 4095, eNB₂ . . . ) Cell Measurement 1 YES ignore Result >CellMeasurement 1 . . . EACH ignore Result Item <maxCelli neNB> >>Cell ID MECGI 9.2.14 >>Hardware Load O 9.2.34 Indicator >>S1 TNL Load O 9.2.35Indicator >>Radio Resource O 9.2.37 Status >>Composite O 9.2.44 YESignore Available Capacity Group >>ABS Status O 9.2.58 YES ignore >>UL-DLSpectral Efficiency

The UL-DL Spectral Efficiency IE may include an indication of theaverage UL and DL spectral efficiency. In one example, the UL-DLSpectral Efficiency IE may be defined as an integer value, e.g., interms of (bit/s)/Hz. In another example, the UL-DL Spectral EfficiencyIE may be defined as an enumerated value.

Reference is made to FIG. 3, which schematically illustrates a method ofTDD UL-DL configuration management, in accordance with somedemonstrative embodiments. In some embodiments, one or more of theoperations of the method of FIG. 3 may be performed by a cellular systeme.g., system 100 (FIG. 1); and/or cellular node, e.g., nodes 106 and/or108 (FIG. 1).

As indicated at block 302, the method may include communicating amessage between a first cellular node and at least one second cellularnode, the message including an indication of a TDD UL-DL configurationallocated by the first node for communication within at least one firstcell controlled by the first node. For example, nodes 106 and 108(FIG. 1) may communicate an X2-AP message including a cell identifieridentifying cell 102 (FIG. 1) and an indication of a TDD UL-DLconfiguration allocated by node 106 for communication within cell 102.

As indicated at block 304, communicating the message may includetransmitting the message by the first node. For example, node 106(FIG. 1) may transmit the message including the indication of the TDDUL-DL configuration allocated by node 106 for communication within cell102.

As indicated at block 306, communicating the message may includereceiving the message at the second node. For example, node 108 (FIG. 1)may receive the message including the indication of the TDD UL-DLconfiguration allocated by node 106 for communication within cell 102.

As indicated at block 308, the method may include allocating a TDD UL-DLconfiguration for communication within a second cell based on the TDDUL-DL configuration updated by the first node. For example, node 108(FIG. 1) may update a TDD UL-DL configuration allocated for cell 104(FIG. 1) based on the TDD UL-DL configuration allocated for cell 102(FIG. 1), as received from node 106 (FIG. 1).

Reference is made to FIG. 4, which schematically illustrates a productof manufacture 400, in accordance with some demonstrative embodiments.Product 400 may include a non-transitory machine-readable storage medium402 to store logic 404, which may be used, for example, to perform atleast part of the functionality of nodes 106 and/or 108 (FIG. 1), TDDUL/DL controller 230 (FIG. 2), wireless communication unit 202 (FIG. 2),and/or to perform one or more operations of the method of FIG. 3. Thephrase “non-transitory machine-readable medium” is directed to includeall computer-readable media, with the sole exception being a transitorypropagating signal.

In some demonstrative embodiments, product 400 and/or machine-readablestorage medium 402 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage medium 402 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 404 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 404 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Matlab,Pascal, Visual BASIC, assembly language, machine code, and the like.

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features have been illustrated and described herein, manyvariations, modifications, substitutions, changes, additions,improvements and equivalents may occur to those skilled in the art. Itis, therefore, to be understood that the appended claims are intended tocover all such modifications and changes as fall within the true spiritof the invention.

What is claimed is:
 1. An evolved node B (eNB), comprising: circuitry tocontrol communication of a message to share load information in anorthogonal frequency-division multiplexing (OFDM)time-division-duplexing (TDD) cellular system, the message having afirst information element (IE) to indicate a cell identifier for a firstwireless communication cell, a second IE to indicate uplink-downlink(UL-DL) configuration information intended to be used by the firstwireless communication cell, and a third IE to indicate a cellidentifier for a second wireless communication cell; and a transceivercoupled to the circuitry, the transceiver to transmit the message asOFDM signals.
 2. The eNB of claim 1, the OFDM TDD cellular systemcomprising a long term evolution (LTE) or LTE advanced (LTE-A) system.3. The eNB of claim 1, the message comprising an X2 application protocol(X2AP) message.
 4. The eNB of claim 1, the message comprising a loadinformation message of an X2 application protocol (X2AP).
 5. The eNB ofclaim 1, the first IE comprising a cell identifier IE of a cellinformation item IE group.
 6. The eNB of claim 1, the second IEcomprising a dynamic subframe assignment IE of a cell information itemIE group, the dynamic subframe assignment IE to indicate the UL-DLconfiguration information as a value within a set of enumerated values,the value to indicate a predefined UL-DL configuration.
 7. The eNB ofclaim 1, the second IE comprising an UL-DL configuration update IE of acell information item IE group, the UL-DL configuration update IE toindicate the UL-DL configuration information as a value within a set ofenumerated values, each enumerated value to indicate a differentpredefined UL-DL configuration.
 8. The eNB of claim 1, the third IEcomprising a target cell identifier IE of an UL high interferenceinformation IE group.
 9. The eNB of claim 1, the transceiver to transmitthe message to an eNB that controls the second wireless communicationcell.
 10. The eNB of claim 1, comprising one or more antennas coupled tothe transceiver, the transceiver to transmit the message as OFDM signalsvia the one or more antennas.
 11. An evolved node B (eNB), comprising: atransceiver to receive a message to share load information in anorthogonal frequency-division multiplexing (OFDM)time-division-duplexing (TDD) cellular system, the message having afirst information element (IE) to indicate a cell identifier for a firstwireless communication cell, a second IE to indicate uplink-downlink(UL-DL) configuration information intended to be used by the firstwireless communication cell, and a third IE to indicate a cellidentifier for a second wireless communication cell; and circuitrycoupled to the transceiver, the circuitry to allocate an UL-DLconfiguration for the second wireless communication cell based at leastin part on the UL-DL configuration information intended to be used bythe first wireless communication cell.
 12. The eNB of claim 11, the OFDMTDD cellular system comprising a long term evolution (LTE) or LTEadvanced (LTE-A) system.
 13. The eNB of claim 11, the message comprisingan X2 application protocol (X2AP) message.
 14. The eNB of claim 11, themessage comprising a load information message of an X2 applicationprotocol (X2AP).
 15. The eNB of claim 11, the first IE comprising a cellidentifier IE of a cell information item IE group.
 16. The eNB of claim11, the second IE comprising a dynamic subframe assignment IE of a cellinformation item IE group, the dynamic subframe assignment IE toindicate the UL-DL configuration information as a value within a set ofenumerated values, the value to indicate a predefined UL-DLconfiguration.
 17. The eNB of claim 11, the second IE comprising anUL-DL configuration update IE of a cell information item IE group, theUL-DL configuration update IE to indicate the UL-DL configurationinformation as a value within a set of enumerated values, eachenumerated value to indicate a different predefined UL-DL configuration.18. The eNB of claim 11, the third IE comprising a target cellidentifier IE of an UL high interference information IE group.
 19. TheeNB of claim 11, the transceiver to receive the message from an eNB thatcontrols the first wireless communication cell.
 20. The eNB of claim 11,comprising one or more antennas coupled to the transceiver, thetransceiver to receive the message via the one or more antennas as OFDMsignals.
 21. An apparatus, comprising: logic, at least a portion ofwhich is implemented in hardware, to control transmission of a loadinformation message of an X2 application protocol (X2AP) over anorthogonal frequency-division multiplexing (OFDM)time-division-duplexing (TDD) cellular system, the load informationmessage having a cell identifier information element (IE) to indicate acell identifier for a wireless communication cell, and anuplink-downlink (UL-DL) configuration update IE to indicate UL-DLconfiguration information intended to be used by the wirelesscommunication cell indicated by the cell identifier; and a radio coupledto the logic, the radio to transmit the load information message as OFDMsignals.
 22. The apparatus of claim 21, the cell identifier IEcomprising part of a cell information item IE group.
 23. The apparatusof claim 21, the UL-DL configuration update IE comprising part of a cellinformation item IE group, the UL-DL configuration update IE to indicatethe UL-DL configuration information as a value within a set ofenumerated values, each enumerated value to indicate a defined UL-DLconfiguration.
 24. The apparatus of claim 21, the load informationmessage having a target cell identifier IE to indicate a differentwireless communication cell, the target cell identifier IE comprisingpart of an UL high interference information IE group.
 25. The apparatusof claim 21, the OFDM TDD cellular system comprising a long termevolution (LTE) or LTE advanced (LTE-A) system.
 26. A method,comprising: generating a message to share load information in anorthogonal frequency-division multiplexing (OFDM)time-division-duplexing (TDD) cellular system, the message having afirst information element (IE) to indicate a cell identifier for a firstwireless communication cell, a second IE to indicate uplink-downlink(UL-DL) configuration information intended to be used by the firstwireless communication cell, and a third IE to indicate a cellidentifier for a second wireless communication cell; and sending theload information message over a communication channel.
 27. The method ofclaim 26, comprising transmitting the load information message as OFDMsignals.
 28. The method of claim 26, comprising sending the loadinformation message over a data network.
 29. The method of claim 26, thecell identifier IE comprising part of a cell information item IE group,and the UL-DL configuration update IE comprising part of a cellinformation item IE group, the UL-DL configuration update IE to indicatethe UL-DL configuration information as a value within a set ofenumerated values, each enumerated value to indicate a defined UL-DLconfiguration.
 30. The method of claim 26, the load information messagehaving a target cell identifier IE to indicate a different wirelesscommunication cell, the target cell identifier IE comprising part of anUL high interference information IE group.